Efficient plmn encoding for 5g

ABSTRACT

A method for decoding PLMN information comprises receiving a message comprising PLMN information for a plurality of cells and determining PLMN information from the message for a first group of cells that comprises at least one cell, each cell of the first group of cells associated with a first core network type. The method further comprises determining PLMN information from the message for a second group of cells that comprises at least one cell, each cell of the second group of cells associated with a second core network type. At least one cell is a part of the first group of cells and the second group of cells. The PLMN information for the at least one cell in the first group of cells and the second group of cells is provided only once.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/650,763, filed Mar. 25, 2020, which is a 371 of InternationalApplication No. PCT/IB2018/057581, filed Sep. 28, 2018, which claims thebenefit of U.S. Application No. 62/564,483, filed Sep. 28, 2017, thedisclosures of which are fully incorporated herein by reference.

TECHNICAL FIELD

Embodiments of the present disclosure are directed to wirelesscommunications and, more particularly, to efficient encoding anddecoding of public land mobile network (PLMN) information for long termevolution (LTE) equipment connected to a fifth generation (5G) corenetwork.

BACKGROUND

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

The Third Generation Partnership Project (3GPP) fifth generation (5G)wireless network includes both a new radio access (NR) and a new corenetwork (5GC). The 5GC offers several new features such as support fornetwork slicing, improved QoS, and latency and battery optimizations inthe form of a new user equipment (UE) state referred to as inactivemode. To provide these features also in long term evolution (LTE) and toenable fast mobility between LTE and NR, the LTE eNB needs to supportconnectivity to 5GC. Together the LTE eNBs and NR gNBs connected to 5GCmake up the next generation radio access network (NG-RAN).

The core network (CN) type(s) that an eNB is connected to is broadcastedin system information (SI). For radio access network (RAN) sharing,where multiple public land mobile networks (PLMNs) are hosted by thesame eNB, the CN type(s) is determined separately for each PLMN. Foreach PLMN the LTE eNB can be connected to: (1) evolved packet core (EPC)only, (2) both EPC and 5GC or (3) 5GC only. Legacy UEs that only supportthe legacy non-access stratum (NAS) protocol (EPC NAS) can only connectto EPC, while new UEs are expected to support both the legacy and thenew NAS protocol (5GC NAS) and can connect to both EPC and 5GC.

Because legacy UEs can only obtain service from cells with EPCconnectivity, a mechanism is needed to prevent the legacy UEs fromcamping on cells which are only connected to 5GC. There are two possiblecases: (a) all PLMNs are connected to 5GC only; or (b) some PLMNs areconnected to 5GC only while some are connected to both EPC and 5GC orEPC only.

For the first scenario, the existing cellBarred flag in SIB1 may be usedto prevent legacy UEs from camping on the cell. This flag is common forall PLMNs and can therefore only be used in the first scenario. Byletting the new UEs (i.e., UEs capable of 5GC NAS) ignore the flag, thelegacy UEs will be blocked while the new UEs are allowed through. Toprovide the current cell barring flag functionality for new UEs, acorresponding new flag may be used in SIB1 for the new UEs (e.g.,“cellBarred-5GC”).

For the second scenario, one possible solution is to broadcast two PLMNlists in SI: the first one is the existing/legacy PLMN list containingthe PLMNs which are connected to EPC, and the second one is a new PLMNlist containing the PLMNs which are connected to 5GC. PLMNs which areconnected to both EPC and 5GC occur on both lists. Because a legacy UEonly reads the legacy PLMN list, it will only select a PLMN and cellwhich is connected to EPC.

SUMMARY

Based on the description above, there currently exist certain challengeswhen a network node is connected to more than one core network type. Forexample, in addition to the public land mobile network (PLMN)information, other cell access related information is broadcasted insystem information block one (SIB1) in longer term evolution (LTE).Because SIB1 is acquired at every cell re-selection and handover, it isimportant to keep its size as small as possible to minimize theacquisition time. Therefore, reducing the size of the PLMN informationis beneficial.

Certain aspects of the present disclosure and their embodiments mayprovide solutions to these or other challenges. As described above, twoseparate PLMN lists may be broadcasted in SIB1 for LTE cells connectedto both evolved packet core (EPC) and fifth generation core (5GC): thefirst one is the existing/legacy PLMN list containing the PLMNs that areconnected to EPC, and the second one is a PLMN list containing the PLMNsthat are connected to 5GC. In the following, the two PLMNs lists arereferred to as the EPC and 5GC PLMN list, respectively.

Particular embodiments reduce the size of the 5GC PLMN list by avoidingduplicating information for PLMNs that are connected to both EPC and5GC. Rather than repeating the PLMN information for the PLMNs in bothlists, the PLMN is only described in the EPC PLMN list and a referenceto this entry is then included in the 5GC PLMN list.

In some embodiments, a bitmap may mark the PLMNs in the EPC PLMN listthat are also connected to 5GC. The 5GC PLMN list may only contain thePLMNs that are connected to 5GC only. As most PLMNs are likely to beconnected to both EPC and 5GC, particular embodiments can significantlyreduce the size of the PLMN information in SIB1.

According to some embodiments, a method performed by a wireless devicefor efficient decoding of PLMN information comprises receiving a messagecomprising PLMN information for a plurality of cells. The method alsoincludes determining PLMN information from the message for a first groupof cells. The first group of cells comprises at least one cell. Eachcell of the first group of cells is associated with a first core networktype. The method additionally includes determining PLMN information fromthe message for a second group of cells. The second group of cellscomprises at least one cell. Each cell of the second group of cells isassociated with a second core network type. A least one cell is a partof the first group of cells and the second group of cells. The PLMNinformation for the at least one cell in the first group of cells andthe second group of cells is provided only once.

In particular embodiments, the PLMN information of the message comprisesa first list associated with the first group of cells and a second listassociated with the second group of cells.

In particular embodiments, determining PLMN information for the at leastone cell that is a part of the first group of cells and the second groupof cells comprises applying a bitmap to the cells of the first group ofcells. Each bit of the bitmap corresponds to a cell in the first groupof cells. The bitmap identifies each cell of the first group of cellsthat is also in the second group of cells. The PLMN information for theat least one cell with respect to the second core network type is basedon the PLMN information for the corresponding cell with respect to thefirst core network type.

In particular embodiments the message comprises a flag to indicates ifthe cellReservedForOperatorUse field per cell in the first group ofcells is valid for the corresponding cell in the second group of cells.

In particular embodiments, determining PLMN information for the secondgroup of cells comprises, for each cell of the second group of cellsthat is also associated with the first group of cells, following areference to the PLMN information in the first group of cells.

In particular embodiments, the method further comprises maintaining afirst list comprising PLMN information for each cell of the first groupof cells and a second list comprising PLMN information for each cell ofthe second group of cells.

In particular embodiments, the message may be a system information blockmessage or an RRC message.

In particular embodiments the method may also include providing userdata and forwarding the user data to a host computer.

According to some embodiments, a method performed by a base station forefficient encoding of PLMN information comprises determining a corenetwork type associated with each cell of a plurality of cells. Themethod also includes identifying at least one cell associated withmultiple core network types. The method further includes transmitting amessage to a wireless device. The message comprises PLMN information foreach cell associated with a first core network type and each cellassociated with only a second core network type. The PLMN informationwith respect to the second core network type for the at least one cellassociated with multiple core network types may be derived from the PLMNinformation associated with the at least one cell with respect to thefirst core network type.

In particular embodiments, the PLMN information of the message comprisesa first list of cells associated with the first core network type and asecond list of cells associated with the second core network type.

In particular embodiments, the method also includes generating a bitmapindicating which cells associated with the first core network type arealso associated with the second core network type.

In particular embodiments, the message comprises the bitmap. In someembodiments the message comprises a flag to indicate if thecellReservedForOperatorUse field per cell in the first group of cells isvalid for the corresponding cell in the second group of cells.

In particular embodiments, the method may further comprise, for each ofthe at least one cell associated with multiple core network types,generating a reference to determine the PLMN information for the atleast one cell with respect to the second core network type based on thePLMN information for the at least one cell with respect to the firstcore network type.

In some embodiments the message may be a system information blockmessage or an RRC message.

Also disclosed is a computer program product comprising a non-transitorycomputer readable medium storing computer readable program code, thecomputer readable program code operable, when executed by processingcircuitry to perform any of the methods performed by the network nodedescribed above.

Certain embodiments may provide one or more of the following technicaladvantage(s) such as reducing the size of PLMN information for LTEconnected to 5GC which in turn shortens the SIB1 acquisition time.Because SIB1 is acquired at cell (re)selection and handover, this inturn reduces cell (re)selection and handover delay.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and theirfeatures and advantages, reference is now made to the followingdescription, taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 is a block diagram illustrating an example wireless network;

FIG. 2 illustrates an example user equipment, according to certainembodiments;

FIG. 3 illustrates a flowchart of an example method in a user equipmentfor decoding public land mobile network (PLMN) information, according tocertain embodiments;

FIG. 4 illustrates a flowchart of an example method in a network nodefor encoding PLMN information, according to certain embodiments;

FIG. 5 illustrates a schematic block diagram of two apparatuses in awireless network, according to certain embodiments;

FIG. 6 illustrates an example virtualization environment, according tocertain embodiments;

FIG. 7 illustrates an example telecommunication network connected via anintermediate network to a host computer, according to certainembodiments;

FIG. 8 illustrates an example host computer communicating via a basestation with a user equipment over a partially wireless connection,according to certain embodiments;

FIG. 9 is a flowchart illustrating a method implemented, according tocertain embodiments;

FIG. 10 is a flowchart illustrating a method implemented in acommunication system, according to certain embodiments;

FIG. 11 is a flowchart illustrating a method implemented in acommunication system, according to certain embodiments; and

FIG. 12 is a flowchart illustrating a method implemented in acommunication system, according to certain embodiments.

DETAILED DESCRIPTION

As described above, certain challenges currently exist when a networknode is connected to more than one core network type. For example, inaddition to the public land mobile network (PLMN) information, othercell access related information is broadcasted in system informationblock one (SIB1) in longer term evolution (LTE). Because SIB1 isacquired at every cell re-selection and handover, it is important tokeep its size as small as possible to minimize the acquisition time.Therefore, reducing the size of the PLMN information is beneficial.

Certain aspects of the present disclosure and their embodiments mayprovide solutions to these or other challenges. Particular embodimentsare described with reference to the accompanying drawings. Otherembodiments, however, are contained within the scope of the subjectmatter disclosed herein. The disclosed subject matter should not beconstrued as limited to only the embodiments set forth herein; rather,these embodiments are provided by way of example to convey the scope ofthe subject matter to those skilled in the art. Particular embodimentsinclude reducing the size of the PLMN information in SIB1 by avoidingduplication of PLMN specific information including PLMN ID for PLMN'sthat are connected to both evolved packet core (EPC) and fifthgeneration core network (5GCN). In some embodiments, if a PLMN isconnected to both EPC and 5GCN, the PLMN information (e.g., PLMN ID,cellReservedForOperatorUse) is included in the EPC PLMN list and areference to this entry is included in the 5GC list. In theseembodiments, the PLMN is only described once, which avoids duplicatingthe same information in two places. Another benefit is that the userequipment (UE) directly sees which PLMNs are connected to both EPC and5GC.

An example of how particular embodiments may be encoded in ASN.1 in TS36.331 is shown below. Note that maxPLMN-r11 (=6) is a constant thatspecifies the maximum number of entries that can be included in thelegacy EPC PLMN list. The example assumes that the same limit is usedalso for the 5GC PLMN list. The field mapped contains the reference tothe EPC PLMN list.

SystemInformationBlockType1 Message

-- ASN1START SystemInformationBlockType1-BR-r13 ::= SystemInformationBlockType1 SystemInformationBlockType1 ::= SEQUENCE { cellAccessRelatedInfo  SEQUENCE {   plmn-IdentityList   PLMN-IdentityList,   trackingAreaCode  TrackingAreaCode,   cellIdentity CellIdentity,   cellBarred  ENUMERATED {barred, notBarred},  intraFreqReselection   ENUMERATED {allowed, notAllowed},  csg-Indication   BOOLEAN,   csg-Identity   CSG-Identity OPTIONAL --Need OR  },  cellSelectionInfo  SEQUENCE {   q-RxLevMin    Q- RxLevMin,  q-RxLevMinOffset   INTEGER (1..8) OPTIONAL -- Need OP  },  p-Max  P-Max OPTIONAL, -- Need OP  freqBandIndicator  FreqBandIndicator, schedulingInfoList  SchedulingInfoList,  tdd-Config   TDD-ConfigOPTIONAL, -- Cond TDD  si-WindowLength   ENUMERATED {    ms1, ms2, ms5,ms10, ms15, ms20,    ms40},  systemInfoValueTag  INTEGER (0..31), nonCriticalExtension  SystemInformationBlockType1-v890-IEs  OPTIONAL }<text omitted> SystemInformationBlockType1-v15xy-IEs ::=  SEQUENCE { cellAccessRelatedInfo-5GC   SEQUENCE {   plmn-IdentityList-5GC   PLMN-IdentityList-5GC,   cellBarred-5GC   ENUMERATED {barred, notBarred}  }, nonCriticalExtension   SEQUENCE { } }  PLMN-IdentityList-5GC ::=SEQUENCE (SIZE (1..maxPLMN-r11))  OF PLMN-IdentityInfo-5GC PLMN-IdentityInfo-5GC ::=   SEQUENCE {  plmn-IdentityInfo CHOICE {    fullInfo PLMN-IdentityInfo,     mapped INTEGER (1..maxPLMN-r11)  } }-- ASN1STOP

In some embodiments, SIB1 may include a separate bitmap to indicatewhether a PLMN in the EPC PLMN list is also connected to 5GC. The lengthof the bitmap is the same as the maximum number of PLMNs and each bitcorresponds to an entry in the EPC PLMN list. If a bit is set, then thecorresponding PLMN is also connected to 5GC. The 5GC PLMN list is stillneeded for the PLMNs that are connected to 5GC only because they do nothave a corresponding entry in the EPC PLMN list. An example of howparticular embodiments can be encoded in ASN.1 in TS 36.331 is shownbelow. The bitmap described above is contained in the fieldplmnsConnectedToEPCand5GC. Also note that, similar to the example above,the maximum number of entries in the 5GC PLMN list is assumed to be thesame as in the EPC PLMN list.

SystemInformationBlockType1 Message

-- ASN1START SystemInformationBlockType1-BR-r13 ::= SystemInformationBlockType1 SystemInformationBlockType1 ::= SEQUENCE { cellAccessRelatedInfo  SEQUENCE {   plmn-IdentityList   PLMN-IdentityList,   trackingAreaCode  TrackingAreaCode,   cellIdentity CellIdentity,   cellBarred  ENUMERATED {barred, notBarred},  intraFreqReselection   ENUMERATED {allowed, notAllowed},  csg-Indication   BOOLEAN,   csg-Identity   CSG-Identity OPTIONAL --Need OR  },  cellSelectionInfo  SEQUENCE {   q-RxLevMin    Q- RxLevMin,  q-RxLevMinOffset   INTEGER (1..8) OPTIONAL -- Need OP  },  p-Max  P-Max OPTIONAL, -- Need OP  freqBandIndicator  FreqBandIndicator, schedulingInfoList  SchedulingInfoList,  tdd-Config   TDD-ConfigOPTIONAL, -- Cond TDD  si-WindowLength   ENUMERATED {    ms1, ms2, ms5,ms10, ms15, ms20,    ms40},  systemInfoValueTag  INTEGER (0..31), nonCriticalExtension  SystemInformationBlockType1-v890-IEs  OPTIONAL }<text omitted> SystemInformationBlockType1-v15xy-IEs ::=  SEQUENCE { cellAccessRelatedInfo-5GC   SEQUENCE {   plmnsConnectedToEPCand5GC  BIT STRING (maxPLMN-r11)),   plmn-IdentityList-5GC   PLMN-IdentityList,   cellBarred-5GC   ENUMERATED {barred, notBarred}  }, nonCriticalExtension   SEQUENCE { } } -- ASN1STOP

Some embodiments include an additional flag alongside the bitmapdescribed above. The flag maps the IE cellReservedForOperatorUse fromEPC to 5GC. The field cellReservedForOperatorUse is part of the PLMNinformation and is defined per PLMN in EPC PLMN list.

The flag indicates if the cellReservedForOperatorUse field per PLMN inthe EPC PLMN list is valid for 5GC as well. If the flag is set, then thevalue of the cellReservedForOperatorUse field is the same for the mappedPLMN (i.e., the PLMN whose bit is set in the bitmap). If the flag is notset, then the cellReservedForOperatorUse field is redefined for each ofthe mapped PLMNs.

One advantage of the additional flag is that thecellReservedForOperatorUse can have different values for EPC and 5GC forPLMNs connected to both EPC and 5GC. The same idea can be applied forother information elements included in the PLMN information that are setfor each of the EPC PLMNs (e.g., the Tracking Area Code (TAC)).

An example of how particular embodiments can be encoded in ASN.1 in TS36.331 is shown below. The 5GC specific value of thecellReservedForOperatorUse field (denotedcellReservedForOperatorUse-5GC) is included in the information elementPLMN-DeltaIdentityInfo-5GC, which is set per PLMN in the list theplmn-DeltaIdentityList-5GC. The number of elements inplmn-DeltaIdentityList-5GC is the same as the number of bits set in thebitmap (i.e., each list element corresponds to a mapped PLMN). Note thatplmn-DeltaIdentityList-5GC is optional and the optionality flagfunctions as the “additional flag” described above.

SystemInformationBlockType1 Message

-- ASN1START SystemInformationBlockType1-BR-r13 ::= SystemInformationBlockType1 SystemInformationBlockType1 ::= SEQUENCE { cellAccessRelatedInfo  SEQUENCE {   plmn-IdentityList   PLMN-IdentityList,   trackingAreaCode  TrackingAreaCode,   cellIdentity CellIdentity,   cellBarred  ENUMERATED {barred, notBarred},  intraFregReselection   ENUMERATED {allowed, notAllowed},  csg-Indication   BOOLEAN,   csg-Identity   CSG-Identity OPTIONAL --Need OR  },  cellSelectionInfo  SEQUENCE {   q-RxLevMin    Q- RxLevMin,  q-RxLevMinOffset   INTEGER (1..8) OPTIONAL -- Need OP  },  p-Max  P-Max OPTIONAL, -- Need OP  freqBandIndicator  FreqBandIndicator, schedulingInfoList  SchedulingInfoList,  tdd-Config   TDD-ConfigOPTIONAL, -- Cond TDD  si-WindowLength   ENUMERATED {    ms1, ms2, ms5,ms10, ms15, ms20,    ms40},  systemInfoValueTag  INTEGER (0..31), nonCriticalExtension  SystemInformationBlockType1-v890-IEs  OPTIONAL }<text omitted> SystemInformationBlockType1-v15xy-IEs ::=   SEQUENCE { cellAccessRelatedInfo-5GC   SEQUENCE {   plmnsConnectedToEPCand5GC  BIT STRING (maxPLMN-r11)),   plmn-DeltaIdentityList-5GC   PLMN-DeltaIdentityList,   plmn-IdentityLisCt-5GC   PLMN- IdentityList,  cellBarred-5GC   ENUMERATED {barred, notBarred}  }, nonCriticalExtension   SEQUENCE { } } PLMN-DeltaIdentityList-5GC ::=SEQUENCE (SIZE (1..maxPLMN- r11)) OF PLMN-DeltaIdentityInfo-5GCPLMN-DeltaIdentityInfo-5GC ::=  SEQUENCE { cellReservedForOperatorUse-5GC  ENUMERATED {reserved, notReserved} } --ASN1STOP

Although the description above assumes the 5GC PLMN information isincluded in SIB1, in other embodiments the PLMN information be includedin another SIB. The reason SIB1 is assumed is because SIB1 is generallyused for cell access related information. To reference a PLMN connectedto EPC and/or 5GC in, for example RRC signaling, each PLMN may beassigned an index. The index can be assigned in various ways.

A first option uses separate index sets for the EPC and the 5GC PLMNs(e.g., the EPC PLMN list is indexed 1 . . . n and the 5GC PLMN list isindexed 1 . . . m). A drawback of the first option is that an indexalone will not indicate what core network is referred to.

A second option indexes the PLMNs in the EPC list 1 . . . n and thePLMN's in the 5GC list from n+1 . . . n+m. An advantage of the secondoption is that it is possible to implicitly indicate core network typesimply by using the PLMN index. However, specific core network is notindicated for index 1 . . . n if a bitmap is used to indicate PLMN'sthat support 5GC from the EPC PLMN list.

A third option is an embodiment where a bitmap indicates which PLMN's inthe EPC-list also support connection to 5GC (but are not listed in the5GC PLMN list). Then it is not sufficient to only index according tooption 2. In this embodiment, indexing could be: EPC list: 1 . . . n;PLMNs in EPC list that also support 5GC (indicated in bitmap): n+1 . . .n+k, where k is the number of PLMN's in the EPC list that also support5GC; and 5GC list: (n+k)+1 . . . (n+k)+m, where m is the number ofPLMN's in the 5GC list.

A fourth option only indexes the PLMN's that support 5GC. In this case,there is no index assigned to the full EPC-list and the indexing willthen instead be according to: PLMNs in EPC list that also support 5GC(indicated in bitmap):1 . . . k, where k is the number of PLMN's in theEPC list that also support 5GC; and 5GC list: k+1 . . . k+m, where m isthe number of PLMN's in the 5GC list.

By using a common index set (e.g., like options 2-4, and in particularoptions 3 and 4 above) a benefit is that the core network is implicitlyindicated by the PLMN index. In this way, if a specific index isreferenced (e.g., in RRC signalling) the specific index not onlyindicates the specific PLMN, but also the specific core network.Separately signalling the core network type is not needed. The same PLMNmay have two different indexes if it supports connection through bothEPC and 5GC. These embodiments with a common index can be applied evenif other parts disclosed herein are not used.

FIG. 1 illustrates an example wireless network, according to certainembodiments. The wireless network may comprise and/or interface with anytype of communication, telecommunication, data, cellular, and/or radionetwork or other similar type of system. In some embodiments, thewireless network may be configured to operate according to specificstandards or other types of predefined rules or procedures. Thus,particular embodiments of the wireless network may implementcommunication standards, such as Global System for Mobile Communications(GSM), Universal Mobile Telecommunications System (UMTS), Long TermEvolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards;wireless local area network (WLAN) standards, such as the IEEE 802.11standards; and/or any other appropriate wireless communication standard,such as the Worldwide Interoperability for Microwave Access (WiMax),Bluetooth, Z-Wave and/or ZigBee standards.

Network 106 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node 160 and WD 110 comprise various components described inmore detail below. These components work together to provide networknode and/or wireless device functionality, such as providing wirelessconnections in a wireless network. In different embodiments, thewireless network may comprise any number of wired or wireless networks,network nodes, base stations, controllers, wireless devices, relaystations, and/or any other components or systems that may facilitate orparticipate in the communication of data and/or signals whether viawired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network.

Examples of network nodes include, but are not limited to, access points(APs) (e.g., radio access points), base stations (BSs) (e.g., radio basestations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Basestations may be categorized based on the amount of coverage they provide(or, stated differently, their transmit power level) and may then alsobe referred to as femto base stations, pico base stations, micro basestations, or macro base stations.

A base station may be a relay node or a relay donor node controlling arelay. A network node may also include one or more (or all) parts of adistributed radio base station such as centralized digital units and/orremote radio units (RRUs), sometimes referred to as Remote Radio Heads(RRHs). Such remote radio units may or may not be integrated with anantenna as an antenna integrated radio. Parts of a distributed radiobase station may also be referred to as nodes in a distributed antennasystem (DAS). Yet further examples of network nodes includemulti-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.

As another example, a network node may be a virtual network node asdescribed in more detail below. More generally, however, network nodesmay represent any suitable device (or group of devices) capable,configured, arranged, and/or operable to enable and/or provide awireless device with access to the wireless network or to provide someservice to a wireless device that has accessed the wireless network.

In FIG. 1, network node 160 includes processing circuitry 170, devicereadable medium 180, interface 190, auxiliary equipment 184, powersource 186, power circuitry 187, and antenna 162. Although network node160 illustrated in the example wireless network of FIG. 1 may representa device that includes the illustrated combination of hardwarecomponents, other embodiments may comprise network nodes with differentcombinations of components.

It is to be understood that a network node comprises any suitablecombination of hardware and/or software needed to perform the tasks,features, functions and methods disclosed herein. Moreover, while thecomponents of network node 160 are depicted as single boxes locatedwithin a larger box, or nested within multiple boxes, in practice, anetwork node may comprise multiple different physical components thatmake up a single illustrated component (e.g., device readable medium 180may comprise multiple separate hard drives as well as multiple RAMmodules).

Similarly, network node 160 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node 160comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node.

In some embodiments, network node 160 may be configured to supportmultiple radio access technologies (RATs). In such embodiments, somecomponents may be duplicated (e.g., separate device readable medium 180for the different RATs) and some components may be reused (e.g., thesame antenna 162 may be shared by the RATs). Network node 160 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node 160, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into thesame or different chip or set of chips and other components withinnetwork node 160.

Processing circuitry 170 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry 170 may include processing informationobtained by processing circuitry 170 by, for example, converting theobtained information into other information, comparing the obtainedinformation or converted information to information stored in thenetwork node, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Processing circuitry 170 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode 160 components, such as device readable medium 180, network node160 functionality.

For example, processing circuitry 170 may execute instructions stored indevice readable medium 180 or in memory within processing circuitry 170.Such functionality may include providing any of the various wirelessfeatures, functions, or benefits discussed herein. In some embodiments,processing circuitry 170 may include a system on a chip (SOC).

In some embodiments, processing circuitry 170 may include one or more ofradio frequency (RF) transceiver circuitry 172 and baseband processingcircuitry 174. In some embodiments, radio frequency (RF) transceivercircuitry 172 and baseband processing circuitry 174 may be on separatechips (or sets of chips), boards, or units, such as radio units anddigital units. In alternative embodiments, part or all of RF transceivercircuitry 172 and baseband processing circuitry 174 may be on the samechip or set of chips, boards, or units

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry 170executing instructions stored on device readable medium 180 or memorywithin processing circuitry 170. In alternative embodiments, some or allof the functionality may be provided by processing circuitry 170 withoutexecuting instructions stored on a separate or discrete device readablemedium, such as in a hard-wired manner. In any of those embodiments,whether executing instructions stored on a device readable storagemedium or not, processing circuitry 170 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry 170 alone or to other components ofnetwork node 160, but are enjoyed by network node 160 as a whole, and/orby end users and the wireless network generally.

Device readable medium 180 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry 170. Device readable medium 180 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry 170 and, utilized by network node 160. Devicereadable medium 180 may be used to store any calculations made byprocessing circuitry 170 and/or any data received via interface 190. Insome embodiments, processing circuitry 170 and device readable medium180 may be considered to be integrated.

Interface 190 is used in the wired or wireless communication ofsignaling and/or data between network node 160, network 106, and/or WDs110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 tosend and receive data, for example to and from network 106 over a wiredconnection. Interface 190 also includes radio front end circuitry 192that may be coupled to, or in certain embodiments a part of, antenna162.

Radio front end circuitry 192 comprises filters 198 and amplifiers 196.Radio front end circuitry 192 may be connected to antenna 162 andprocessing circuitry 170. Radio front end circuitry may be configured tocondition signals communicated between antenna 162 and processingcircuitry 170. Radio front end circuitry 192 may receive digital datathat is to be sent out to other network nodes or WDs via a wirelessconnection. Radio front end circuitry 192 may convert the digital datainto a radio signal having the appropriate channel and bandwidthparameters using a combination of filters 198 and/or amplifiers 196. Theradio signal may then be transmitted via antenna 162. Similarly, whenreceiving data, antenna 162 may collect radio signals which are thenconverted into digital data by radio front end circuitry 192. Thedigital data may be passed to processing circuitry 170. In otherembodiments, the interface may comprise different components and/ordifferent combinations of components.

In certain alternative embodiments, network node 160 may not includeseparate radio front end circuitry 192, instead, processing circuitry170 may comprise radio front end circuitry and may be connected toantenna 162 without separate radio front end circuitry 192. Similarly,in some embodiments, all or some of RF transceiver circuitry 172 may beconsidered a part of interface 190. In still other embodiments,interface 190 may include one or more ports or terminals 194, radiofront end circuitry 192, and RF transceiver circuitry 172, as part of aradio unit (not shown), and interface 190 may communicate with basebandprocessing circuitry 174, which is part of a digital unit (not shown).

Antenna 162 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna 162 may becoupled to radio front end circuitry 190 and may be any type of antennacapable of transmitting and receiving data and/or signals wirelessly. Insome embodiments, antenna 162 may comprise one or more omni-directional,sector or panel antennas operable to transmit/receive radio signalsbetween, for example, 2 GHz and 66 GHz. An omni-directional antenna maybe used to transmit/receive radio signals in any direction, a sectorantenna may be used to transmit/receive radio signals from deviceswithin a particular area, and a panel antenna may be a line of sightantenna used to transmit/receive radio signals in a relatively straightline. In some instances, the use of more than one antenna may bereferred to as MIMO. In certain embodiments, antenna 162 may be separatefrom network node 160 and may be connectable to network node 160 throughan interface or port.

Antenna 162, interface 190, and/or processing circuitry 170 may beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna 162, interface 190, and/or processing circuitry 170 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry 187 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network node 160with power for performing the functionality described herein. Powercircuitry 187 may receive power from power source 186. Power source 186and/or power circuitry 187 may be configured to provide power to thevarious components of network node 160 in a form suitable for therespective components (e.g., at a voltage and current level needed foreach respective component). Power source 186 may either be included in,or external to, power circuitry 187 and/or network node 160.

For example, network node 160 may be connectable to an external powersource (e.g., an electricity outlet) via an input circuitry or interfacesuch as an electrical cable, whereby the external power source suppliespower to power circuitry 187. As a further example, power source 186 maycomprise a source of power in the form of a battery or battery packwhich is connected to, or integrated in, power circuitry 187. Thebattery may provide backup power should the external power source fail.Other types of power sources, such as photovoltaic devices, may also beused.

Alternative embodiments of network node 160 may include additionalcomponents beyond those shown in FIG. 1 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node 160 may include user interface equipment to allow input ofinformation into network node 160 and to allow output of informationfrom network node 160. This may allow a user to perform diagnostic,maintenance, repair, and other administrative functions for network node160.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD may be used interchangeably herein with user equipment (UE).Communicating wirelessly may involve transmitting and/or receivingwireless signals using electromagnetic waves, radio waves, infraredwaves, and/or other types of signals suitable for conveying informationthrough air.

In some embodiments, a WD may be configured to transmit and/or receiveinformation without direct human interaction. For instance, a WD may bedesigned to transmit information to a network on a predeterminedschedule, when triggered by an internal or external event, or inresponse to requests from the network.

Examples of a WD include, but are not limited to, a smart phone, amobile phone, a cell phone, a voice over IP (VoIP) phone, a wirelesslocal loop phone, a desktop computer, a personal digital assistant(PDA), a wireless cameras, a gaming console or device, a music storagedevice, a playback appliance, a wearable terminal device, a wirelessendpoint, a mobile station, a tablet, a laptop, a laptop-embeddedequipment (LEE), a laptop-mounted equipment (LME), a smart device, awireless customer-premise equipment (CPE). a vehicle-mounted wirelessterminal device, etc. A WD may support device-to-device (D2D)communication, for example by implementing a 3GPP standard for sidelinkcommunication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure(V2I), vehicle-to-everything (V2X) and may in this case be referred toas a D2D communication device.

As yet another specific example, in an Internet of Things (IoT)scenario, a WD may represent a machine or other device that performsmonitoring and/or measurements and transmits the results of suchmonitoring and/or measurements to another WD and/or a network node. TheWD may in this case be a machine-to-machine (M2M) device, which may in a3GPP context be referred to as an MTC device. As one example, the WD maybe a UE implementing the 3GPP narrow band internet of things (NB-IoT)standard. Examples of such machines or devices are sensors, meteringdevices such as power meters, industrial machinery, or home or personalappliances (e.g. refrigerators, televisions, etc.) personal wearables(e.g., watches, fitness trackers, etc.).

In other scenarios, a WD may represent a vehicle or other equipment thatis capable of monitoring and/or reporting on its operational status orother functions associated with its operation. A WD as described abovemay represent the endpoint of a wireless connection, in which case thedevice may be referred to as a wireless terminal. Furthermore, a WD asdescribed above may be mobile, in which case it may also be referred toas a mobile device or a mobile terminal.

As illustrated, wireless device 110 includes antenna 111, interface 114,processing circuitry 120, device readable medium 130, user interfaceequipment 132, auxiliary equipment 134, power source 136 and powercircuitry 137. WD 110 may include multiple sets of one or more of theillustrated components for different wireless technologies supported byWD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, orBluetooth wireless technologies, just to mention a few. These wirelesstechnologies may be integrated into the same or different chips or setof chips as other components within WD 110.

Antenna 111 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface 114. In certain alternative embodiments, antenna 111 may beseparate from WD 110 and be connectable to WD 110 through an interfaceor port. Antenna 111, interface 114, and/or processing circuitry 120 maybe configured to perform any receiving or transmitting operationsdescribed herein as being performed by a WD. Any information, dataand/or signals may be received from a network node and/or another WD. Insome embodiments, radio front end circuitry and/or antenna 111 may beconsidered an interface.

As illustrated, interface 114 comprises radio front end circuitry 112and antenna 111. Radio front end circuitry 112 comprise one or morefilters 118 and amplifiers 116. Radio front end circuitry 114 isconnected to antenna 111 and processing circuitry 120 and is configuredto condition signals communicated between antenna 111 and processingcircuitry 120. Radio front end circuitry 112 may be coupled to or a partof antenna 111. In some embodiments, WD 110 may not include separateradio front end circuitry 112; rather, processing circuitry 120 maycomprise radio front end circuitry and may be connected to antenna 111.Similarly, in some embodiments, some or all of RF transceiver circuitry122 may be considered a part of interface 114.

Radio front end circuitry 112 may receive digital data that is to besent out to other network nodes or WDs via a wireless connection. Radiofront end circuitry 112 may convert the digital data into a radio signalhaving the appropriate channel and bandwidth parameters using acombination of filters 118 and/or amplifiers 116. The radio signal maythen be transmitted via antenna 111. Similarly, when receiving data,antenna 111 may collect radio signals which are then converted intodigital data by radio front end circuitry 112. The digital data may bepassed to processing circuitry 120. In other embodiments, the interfacemay comprise different components and/or different combinations ofcomponents.

Processing circuitry 120 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD 110components, such as device readable medium 130, WD 110 functionality.Such functionality may include providing any of the various wirelessfeatures or benefits discussed herein. For example, processing circuitry120 may execute instructions stored in device readable medium 130 or inmemory within processing circuitry 120 to provide the functionalitydisclosed herein.

As illustrated, processing circuitry 120 includes one or more of RFtransceiver circuitry 122, baseband processing circuitry 124, andapplication processing circuitry 126. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitry120 of WD 110 may comprise a SOC. In some embodiments, RF transceivercircuitry 122, baseband processing circuitry 124, and applicationprocessing circuitry 126 may be on separate chips or sets of chips.

In alternative embodiments, part or all of baseband processing circuitry124 and application processing circuitry 126 may be combined into onechip or set of chips, and RF transceiver circuitry 122 may be on aseparate chip or set of chips. In still alternative embodiments, part orall of RF transceiver circuitry 122 and baseband processing circuitry124 may be on the same chip or set of chips, and application processingcircuitry 126 may be on a separate chip or set of chips. In yet otheralternative embodiments, part or all of RF transceiver circuitry 122,baseband processing circuitry 124, and application processing circuitry126 may be combined in the same chip or set of chips. In someembodiments, RF transceiver circuitry 122 may be a part of interface114. RF transceiver circuitry 122 may condition RF signals forprocessing circuitry 120.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry 120 executing instructions stored on device readable medium130, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry 120 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner.

In any of those embodiments, whether executing instructions stored on adevice readable storage medium or not, processing circuitry 120 can beconfigured to perform the described functionality. The benefits providedby such functionality are not limited to processing circuitry 120 aloneor to other components of WD 110, but are enjoyed by WD 110, and/or byend users and the wireless network generally.

Processing circuitry 120 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry 120, may include processinginformation obtained by processing circuitry 120 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD 110, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium 130 may be operable to store a computer program,software, an application including one or more of logic, rules, code,tables, etc. and/or other instructions capable of being executed byprocessing circuitry 120. Device readable medium 130 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry 120. In someembodiments, processing circuitry 120 and device readable medium 130 maybe integrated.

User interface equipment 132 may provide components that allow for ahuman user to interact with WD 110. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipment132 may be operable to produce output to the user and to allow the userto provide input to WD 110. The type of interaction may vary dependingon the type of user interface equipment 132 installed in WD 110. Forexample, if WD 110 is a smart phone, the interaction may be via a touchscreen; if WD 110 is a smart meter, the interaction may be through ascreen that provides usage (e.g., the number of gallons used) or aspeaker that provides an audible alert (e.g., if smoke is detected).

User interface equipment 132 may include input interfaces, devices andcircuits, and output interfaces, devices and circuits. User interfaceequipment 132 is configured to allow input of information into WD 110and is connected to processing circuitry 120 to allow processingcircuitry 120 to process the input information. User interface equipment132 may include, for example, a microphone, a proximity or other sensor,keys/buttons, a touch display, one or more cameras, a USB port, or otherinput circuitry. User interface equipment 132 is also configured toallow output of information from WD 110, and to allow processingcircuitry 120 to output information from WD 110. User interfaceequipment 132 may include, for example, a speaker, a display, vibratingcircuitry, a USB port, a headphone interface, or other output circuitry.Using one or more input and output interfaces, devices, and circuits, ofuser interface equipment 132, WD 110 may communicate with end usersand/or the wireless network and allow them to benefit from thefunctionality described herein.

Auxiliary equipment 134 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment 134 may vary depending on the embodiment and/or scenario.

Power source 136 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD 110 may further comprise power circuitry 137for delivering power from power source 136 to the various parts of WD110 which need power from power source 136 to carry out anyfunctionality described or indicated herein. Power circuitry 137 may incertain embodiments comprise power management circuitry.

Power circuitry 137 may additionally or alternatively be operable toreceive power from an external power source; in which case WD 110 may beconnectable to the external power source (such as an electricity outlet)via input circuitry or an interface such as an electrical power cable.Power circuitry 137 may also in certain embodiments be operable todeliver power from an external power source to power source 136. Thismay be, for example, for the charging of power source 136. Powercircuitry 137 may perform any formatting, converting, or othermodification to the power from power source 136 to make the powersuitable for the respective components of WD 110 to which power issupplied.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 1. Forsimplicity, the wireless network of FIG. 1 only depicts network 106,network nodes 160 and 160 b, and WDs 110, 110 b, and 110 c. In practice,a wireless network may further include any additional elements suitableto support communication between wireless devices or between a wirelessdevice and another communication device, such as a landline telephone, aservice provider, or any other network node or end device. Of theillustrated components, network node 160 and wireless device (WD) 110are depicted with additional detail. The wireless network may providecommunication and other types of services to one or more wirelessdevices to facilitate the wireless devices' access to and/or use of theservices provided by, or via, the wireless network.

FIG. 2 illustrates an example user equipment, according to certainembodiments. As used herein, a user equipment or UE may not necessarilyhave a user in the sense of a human user who owns and/or operates therelevant device. Instead, a UE may represent a device that is intendedfor sale to, or operation by, a human user but which may not, or whichmay not initially, be associated with a specific human user (e.g., asmart sprinkler controller). Alternatively, a UE may represent a devicethat is not intended for sale to, or operation by, an end user but whichmay be associated with or operated for the benefit of a user (e.g., asmart power meter). UE 200 may be any UE identified by the 3^(rd)Generation Partnership Project (3GPP), including a NB-IoT UE, a machinetype communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 200,as illustrated in FIG. 2, is one example of a WD configured forcommunication in accordance with one or more communication standardspromulgated by the 3^(rd) Generation Partnership Project (3GPP), such as3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, theterm WD and UE may be used interchangeable. Accordingly, although FIG. 2is a UE, the components discussed herein are equally applicable to a WD,and vice-versa.

In FIG. 2, UE 200 includes processing circuitry 201 that is operativelycoupled to input/output interface 205, radio frequency (RF) interface209, network connection interface 211, memory 215 including randomaccess memory (RAM) 217, read-only memory (ROM) 219, and storage medium221 or the like, communication subsystem 231, power source 233, and/orany other component, or any combination thereof. Storage medium 221includes operating system 223, application program 225, and data 227. Inother embodiments, storage medium 221 may include other similar types ofinformation. Certain UEs may utilize all of the components shown in FIG.2, or only a subset of the components. The level of integration betweenthe components may vary from one UE to another UE. Further, certain UEsmay contain multiple instances of a component, such as multipleprocessors, memories, transceivers, transmitters, receivers, etc.

In FIG. 2, processing circuitry 201 may be configured to processcomputer instructions and data. Processing circuitry 201 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry 201 may include twocentral processing units (CPUs). Data may be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface 205 may be configuredto provide a communication interface to an input device, output device,or input and output device. UE 200 may be configured to use an outputdevice via input/output interface 205.

An output device may use the same type of interface port as an inputdevice. For example, a USB port may be used to provide input to andoutput from UE 200. The output device may be a speaker, a sound card, avideo card, a display, a monitor, a printer, an actuator, an emitter, asmartcard, another output device, or any combination thereof.

UE 200 may be configured to use an input device via input/outputinterface 205 to allow a user to capture information into UE 200. Theinput device may include a touch-sensitive or presence-sensitivedisplay, a camera (e.g., a digital camera, a digital video camera, a webcamera, etc.), a microphone, a sensor, a mouse, a trackball, adirectional pad, a trackpad, a scroll wheel, a smartcard, and the like.The presence-sensitive display may include a capacitive or resistivetouch sensor to sense input from a user. A sensor may be, for instance,an accelerometer, a gyroscope, a tilt sensor, a force sensor, amagnetometer, an optical sensor, a proximity sensor, another likesensor, or any combination thereof. For example, the input device may bean accelerometer, a magnetometer, a digital camera, a microphone, and anoptical sensor.

In FIG. 2, RF interface 209 may be configured to provide a communicationinterface to RF components such as a transmitter, a receiver, and anantenna. Network connection interface 211 may be configured to provide acommunication interface to network 243 a. Network 243 a may encompasswired and/or wireless networks such as a local-area network (LAN), awide-area network (WAN), a computer network, a wireless network, atelecommunications network, another like network or any combinationthereof. For example, network 243 a may comprise a Wi-Fi network.Network connection interface 211 may be configured to include a receiverand a transmitter interface used to communicate with one or more otherdevices over a communication network according to one or morecommunication protocols, such as Ethernet, TCP/IP, SONET, ATM, or thelike. Network connection interface 211 may implement receiver andtransmitter functionality appropriate to the communication network links(e.g., optical, electrical, and the like). The transmitter and receiverfunctions may share circuit components, software or firmware, oralternatively may be implemented separately.

RAM 217 may be configured to interface via bus 202 to processingcircuitry 201 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM 219 maybe configured to provide computer instructions or data to processingcircuitry 201. For example, ROM 219 may be configured to store invariantlow-level system code or data for basic system functions such as basicinput and output (I/O), startup, or reception of keystrokes from akeyboard that are stored in a non-volatile memory.

Storage medium 221 may be configured to include memory such as RAM, ROM,programmable read-only memory (PROM), erasable programmable read-onlymemory (EPROM), electrically erasable programmable read-only memory(EEPROM), magnetic disks, optical disks, floppy disks, hard disks,removable cartridges, or flash drives. In one example, storage medium221 may be configured to include operating system 223, applicationprogram 225 such as a web browser application, a widget or gadget engineor another application, and data file 227. Storage medium 221 may store,for use by UE 200, any of a variety of various operating systems orcombinations of operating systems.

Storage medium 221 may be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium 221 may allow UE 200 to access computer-executable instructions,application programs or the like, stored on transitory or non-transitorymemory media, to off-load data, or to upload data. An article ofmanufacture, such as one utilizing a communication system may betangibly embodied in storage medium 221, which may comprise a devicereadable medium.

In FIG. 2, processing circuitry 201 may be configured to communicatewith network 243 b using communication subsystem 231. Network 243 a andnetwork 243 b may be the same network or networks or different networkor networks. Communication subsystem 231 may be configured to includeone or more transceivers used to communicate with network 243 b. Forexample, communication subsystem 231 may be configured to include one ormore transceivers used to communicate with one or more remotetransceivers of another device capable of wireless communication such asanother WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.2,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver mayinclude transmitter 233 and/or receiver 235 to implement transmitter orreceiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter 233 andreceiver 235 of each transceiver may share circuit components, softwareor firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem 231 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem 231 may include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network 243 b may encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, network243 b may be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source 213 may be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE 200.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE 200 or partitioned acrossmultiple components of UE 200. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystem231 may be configured to include any of the components described herein.Further, processing circuitry 201 may be configured to communicate withany of such components over bus 202. In another example, any of suchcomponents may be represented by program instructions stored in memorythat when executed by processing circuitry 201 perform the correspondingfunctions described herein. In another example, the functionality of anyof such components may be partitioned between processing circuitry 201and communication subsystem 231. In another example, thenon-computationally intensive functions of any of such components may beimplemented in software or firmware and the computationally intensivefunctions may be implemented in hardware.

FIG. 3 illustrates a flowchart of an example method in a user equipmentfor decoding PLMN information, according to certain embodiments. Inparticular embodiments, one or more steps of FIG. 3 may be performed bywireless device 110 described with respect to FIG. 1.

The method begins at step 3112, where the wireless device receives thefirst message comprising the PLMN information for a plurality of cells.In some embodiments, the PLMN information may comprise a list of PLMNinformation for cells associated with the first core network type (e.g.,EPC) and a list of PLMN information for cells associated with only thesecond core network type (e.g., 5GC). For those cells that areassociated with both (e.g., EPC and 5GC), the PLMN information isprovided only with respect to the list for the first core network type.

At step 3114, the wireless device determines the PLMN information fromthe first message for a first group of cells associated with the firstcore network type. For example, the wireless device may retrieve PLMNinformation for a group of cells associated with an EPC core network.

At step 3116, the wireless device determines PLMN information from thefirst message for a second group of cells. The second group of cellscomprises at least one cell. Each cell of the second group of cells isassociated with a second core network type (e.g., 5GC) and at least onecell is a part of the first group of cells and the second group of cells(e.g., EPC and 5GC).

The PLMN information for the at least one cell in the first group ofcells and the second group of cells is provided only once. That is,rather than provide the PLMN information for the cell with respect tothe first core network type and again for the same cell for the secondcore network type, the PLMN is provided once with respect to the firstcore network type and then used again to derive the PLMN information forthe cell with respect to the second core network type.

The PLMN information for those cells associated with both core networktypes may be determined in a variety of different ways. For example, thewireless device may apply a bitmap to the cells of the first group ofcells. Each bit of the bitmap corresponds to a cell in the first groupof cells, such that if a bit is set (e.g., 1) then the PLMN informationfor that cell may be used or copied for that corresponding cell withrespect to the second network core type.

As another example, for each cell that has an association with both thefirst and second network core types, the first message may include areference a reference for the second core network type to acorresponding cell associated with the first core network type. Forexample, in the list of cells that are associated with the secondnetwork core type, there may be one or more references (depending on thenumber of cells that are associated with multiple core network types) toPLMN information in the list of cells that are associated with the firstnetwork core type. Particular embodiments may include any of theembodiments and examples described above for indicating which cells arepart of which group.

At step 3118, the wireless device may maintain a first list comprisingPLMN information for each cell of the first group of cells and a secondlist comprising PLMN information for each cell of the second group ofcells.

Modifications, additions, or omissions may be made to method 3100 ofFIG. 3. Additionally, one or more steps in the method of FIG. 3 may beperformed in parallel or in any suitable order.

FIG. 4 illustrates a flowchart of an example method in a network nodefor encoding PLMN information, according to certain embodiments. Inparticular embodiments, one or more steps of FIG. 4 may be performed bynetwork node 160 described with respect to FIG. 1.

The method begins at step 4112, where the network node determines a corenetwork type associated with each cell of a plurality of cells. Forexample, network node 160 may determine whether a cell is connected to aEPC core network or a 5GC core network. Network node 160 may receive theinformation from network nodes 160 of the other cells, network node 160may receive the information from its core network, network node 160 maybe provisioned with the core network type associated with other cells,or network node 160 may determine the core network type in any othersuitable manner.

At step 4114, the network node identifies at least one cell associatedwith multiple core network types. For example, a cell that is associatedwith an EPC and with a 5GC. Each of the cells identified as beingassociated with multiple core network types may only have the PLMNinformation provided once, along with a way to derive the PLMNinformation for the other/additional core network types.

For example, at step 4116 the network node could generate a bitmap toindicate which cells are associated with both core network types. Asanother example, at step 4118 the network node could provide a referenceto the other/additional core network type from which the wireless devicecan determine the PLMN information.

At step 4118 the network node transmits a message to a wireless device.The message comprises PLMN information for each cell associated with afirst core network type and each cell associated with only a second corenetwork type. For those cells associated with multiple core networktypes, rather than repeat the PLMN information for the second corenetwork type, the message may comprise information that can be used toderive the PLMN informant for the second core network type. In someembodiments, the first message may be a system information block message(e.g., SIB1). In some embodiments, the first message may be an RRCmessage.

Modifications, additions, or omissions may be made to method 4100 ofFIG. 4. Additionally, one or more steps in the method of FIG. 4 may beperformed in parallel or in any suitable order.

FIG. 5 illustrates a schematic block diagram of two apparatuses in awireless network (for example, the wireless network illustrated in FIG.1). The apparatuses include a wireless device and a network node (e.g.,wireless device 110 or network node 160 illustrated in FIG. 1).Apparatuses 1600 and 1700 are operable to carry out the example methodsdescribed with reference to FIGS. 3 and 4, respectively, and possiblyany other processes or methods disclosed herein. It is also to beunderstood that the method of FIGS. 3 and 4 are not necessarily carriedout solely by apparatus 1600 and/or apparatus 1700. At least someoperations of the method can be performed by one or more other entities.

Virtual apparatuses 1600 and 1700 may comprise processing circuitry,which may include one or more microprocessor or microcontrollers, aswell as other digital hardware, which may include digital signalprocessors (DSPs), special-purpose digital logic, and the like. Theprocessing circuitry may be configured to execute program code stored inmemory, which may include one or several types of memory such asread-only memory (ROM), random-access memory, cache memory, flash memorydevices, optical storage devices, etc. Program code stored in memoryincludes program instructions for executing one or moretelecommunications and/or data communications protocols as well asinstructions for carrying out one or more of the techniques describedherein, in several embodiments.

In some implementations, the processing circuitry may be used to causereceiver unit 1602, determination unit 1606, and maintaining unit 1608,and any other suitable units of apparatus 1600 to perform correspondingfunctions according one or more embodiments of the present disclosure.Similarly, the processing circuitry described above may be used to causedetermination unit 1712, identification unit 1714, and transmission unit1716 and any other suitable units of apparatus 1700 to performcorresponding functions according one or more embodiments of the presentdisclosure

As illustrated in FIG. 5, apparatus 1600 includes receiver unit 1602configured to receive a first message comprising PLMN information for aplurality of cells. In some embodiments, the PLMN information of thefirst message comprises a first list associated with the first group ofcells and a second list associated with the second group of cells. Insome embodiments, the first message may comprise a flag to indicate ifthe cellReservedForOperatorUse field per cell in the first group ofcells is valid for the corresponding cell in the second group of cells.In some embodiments, the first message is a system information blockmessage. In some embodiments, the first message is an RRC message.

Apparatus 1600 also includes determination unit 1606 configured todetermine PLMN information from the first message for a first and secondgroup of cells. The first group of cells comprises at least one cell.Each cell of the first group of cells is associated with a first corenetwork type. Some of them may also be associated with a second corenetwork type.

The second group of cells comprises at least one cell. Each cell of thesecond group of cells is associated with a second core network type. Atleast one cell is a part of the first group of cells and the secondgroup of cells. The PLMN information for the at least one cell in thefirst group of cells and the second group of cells is provided onlyonce.

For example, with respect to the first group of cells some embodimentsmay use a bitmap that is applied to the first group of cells to identifywhich of those cells are associated with both network core types. Then,once identified, the PLMN information from those cells may be reused orcopied for the second group of cells. As another example, thedetermination may be done by, for each cell of the second group of cellsthat is also associated with the first group of cells, following areference to the PLMN information in the first group of cells

Apparatus 1600 also includes maintaining unit 1608 configured tomaintain a first list comprising PLMN information for each cell of thefirst group of cells and a second list comprising PLMN information foreach cell of the second group of cells. Some of the PLMN information maybe duplicated in the two lists.

As illustrated in FIG. 5, apparatus 1700 includes determination unit1712 configured to determine a core network type associated with eachcell of a plurality of cells. In some embodiments, determination unit1712 may be further configured to generate a bitmap indicating whichcells of associated with the first core network type are also associatedwith the second core network type. In some embodiments, for each of theat least one cell associated with multiple core network typesdetermination unit 1712 may be configured to generate a reference thatmay be used to determine the PLMN information for the at least one cellwith respect to the second core network type based on the PLMNinformation for the at least one cell with respect to the first corenetwork type.

Apparatus 1700 also includes identification unit 1714 configured toidentify at least one cell associated with multiple core network types.

Apparatus 1700 also includes transmission unit 1716 configured totransmit a message to a wireless device. The message comprises PLMNinformation for each cell associated with a first core network type andeach cell associated with only a second core network type wherein thePLMN information with respect to the second core network type for the atleast one cell associated with multiple core network types may bederived from the PLMN information associated with the at least one cellwith respect to the first core network type.

In some embodiments, the first message may comprise a flag to indicateif the cellReservedForOperatorUse field per cell in the first group ofcells is valid for the corresponding cell in the second group of cells.In some embodiments the first message is a system information blockmessage. In some embodiments the first message is an RRC message. Insome embodiments the PLMN information of the first message comprises afirst list of cells associated with the first core network type and asecond list of cells associated with the second core network type.

FIG. 6 is a schematic block diagram illustrating a virtualizationenvironment 300 in which functions implemented by some embodiments maybe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments 300 hosted byone or more of hardware nodes 330. Further, in embodiments in which thevirtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications 320 (whichmay alternatively be called software instances, virtual appliances,network functions, virtual nodes, virtual network functions, etc.)operative to implement some of the features, functions, and/or benefitsof some of the embodiments disclosed herein. Applications 320 are run invirtualization environment 300 which provides hardware 330 comprisingprocessing circuitry 360 and memory 390. Memory 390 containsinstructions 395 executable by processing circuitry 360 wherebyapplication 320 is operative to provide one or more of the features,benefits, and/or functions disclosed herein.

Virtualization environment 300, comprises general-purpose orspecial-purpose network hardware devices 330 comprising a set of one ormore processors or processing circuitry 360, which may be commercialoff-the-shelf (COTS) processors, dedicated Application SpecificIntegrated Circuits (ASICs), or any other type of processing circuitryincluding digital or analog hardware components or special purposeprocessors. Each hardware device may comprise memory 390-1 which may benon-persistent memory for temporarily storing instructions 395 orsoftware executed by processing circuitry 360. Each hardware device maycomprise one or more network interface controllers (NICs) 370, alsoknown as network interface cards, which include physical networkinterface 380. Each hardware device may also include non-transitory,persistent, machine-readable storage media 390-2 having stored thereinsoftware 395 and/or instructions executable by processing circuitry 360.Software 395 may include any type of software including software forinstantiating one or more virtualization layers 350 (also referred to ashypervisors), software to execute virtual machines 340 as well assoftware allowing it to execute functions, features and/or benefitsdescribed in relation with some embodiments described herein.

Virtual machines 340, comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer 350 or hypervisor. Differentembodiments of the instance of virtual appliance 320 may be implementedon one or more of virtual machines 340, and the implementations may bemade in different ways.

During operation, processing circuitry 360 executes software 395 toinstantiate the hypervisor or virtualization layer 350, which maysometimes be referred to as a virtual machine monitor (VMM).Virtualization layer 350 may present a virtual operating platform thatappears like networking hardware to virtual machine 340.

As shown in FIG. 6, hardware 330 may be a standalone network node withgeneric or specific components. Hardware 330 may comprise antenna 3225and may implement some functions via virtualization. Alternatively,hardware 330 may be part of a larger cluster of hardware (e.g. such asin a data center or customer premise equipment (CPE)) where manyhardware nodes work together and are managed via management andorchestration (MANO) 3100, which, among others, oversees lifecyclemanagement of applications 320.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high-volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine 340 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines 340, and that part of hardware 330 that executes that virtualmachine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines 340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines 340 on top of hardware networking infrastructure330 and corresponds to application 320 in FIG. 18.

In some embodiments, one or more radio units 3200 that each include oneor more transmitters 3220 and one or more receivers 3210 may be coupledto one or more antennas 3225. Radio units 3200 may communicate directlywith hardware nodes 330 via one or more appropriate network interfacesand may be used in combination with the virtual components to provide avirtual node with radio capabilities, such as a radio access node or abase station.

In some embodiments, some signaling can be effected with the use ofcontrol system 3230 which may alternatively be used for communicationbetween the hardware nodes 330 and radio units 3200.

With reference to FIG. 7, in accordance with an embodiment, acommunication system includes telecommunication network 410, such as a3GPP-type cellular network, which comprises access network 411, such asa radio access network, and core network 414. Access network 411comprises a plurality of base stations 412 a, 412 b, 412 c, such as NBs,eNBs, gNBs or other types of wireless access points, each defining acorresponding coverage area 413 a, 413 b, 413 c. Each base station 412a, 412 b, 412 c is connectable to core network 414 over a wired orwireless connection 415. A first UE 491 located in coverage area 413 cis configured to wirelessly connect to, or be paged by, thecorresponding base station 412 c. A second UE 492 in coverage area 413 ais wirelessly connectable to the corresponding base station 412 a. Whilea plurality of UEs 491, 492 are illustrated in this example, thedisclosed embodiments are equally applicable to a situation where a soleUE is in the coverage area or where a sole UE is connecting to thecorresponding base station 412.

Telecommunication network 410 is itself connected to host computer 430,which may be embodied in the hardware and/or software of a standaloneserver, a cloud-implemented server, a distributed server or asprocessing resources in a server farm. Host computer 430 may be underthe ownership or control of a service provider, or may be operated bythe service provider or on behalf of the service provider. Connections421 and 422 between telecommunication network 410 and host computer 430may extend directly from core network 414 to host computer 430 or may govia an optional intermediate network 420. Intermediate network 420 maybe one of, or a combination of more than one of, a public, private orhosted network; intermediate network 420, if any, may be a backbonenetwork or the Internet; in particular, intermediate network 420 maycomprise two or more sub-networks (not shown).

The communication system of FIG. 7 as a whole enables connectivitybetween the connected UEs 491, 492 and host computer 430. Theconnectivity may be described as an over-the-top (OTT) connection 450.Host computer 430 and the connected UEs 491, 492 are configured tocommunicate data and/or signaling via OTT connection 450, using accessnetwork 411, core network 414, any intermediate network 420 and possiblefurther infrastructure (not shown) as intermediaries. OTT connection 450may be transparent in the sense that the participating communicationdevices through which OTT connection 450 passes are unaware of routingof uplink and downlink communications. For example, base station 412 maynot or need not be informed about the past routing of an incomingdownlink communication with data originating from host computer 430 tobe forwarded (e.g., handed over) to a connected UE 491. Similarly, basestation 412 need not be aware of the future routing of an outgoinguplink communication originating from the UE 491 towards the hostcomputer 430.

FIG. 8 illustrates an example host computer communicating via a basestation with a user equipment over a partially wireless connection,according to certain embodiments. Example implementations, in accordancewith an embodiment, of the UE, base station and host computer discussedin the preceding paragraphs will now be described with reference to FIG.20. In communication system 500, host computer 510 comprises hardware515 including communication interface 516 configured to set up andmaintain a wired or wireless connection with an interface of a differentcommunication device of communication system 500. Host computer 510further comprises processing circuitry 518, which may have storageand/or processing capabilities. In particular, processing circuitry 518may comprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. Host computer 510further comprises software 511, which is stored in or accessible by hostcomputer 510 and executable by processing circuitry 518. Software 511includes host application 512. Host application 512 may be operable toprovide a service to a remote user, such as UE 530 connecting via OTTconnection 550 terminating at UE 530 and host computer 510. In providingthe service to the remote user, host application 512 may provide userdata which is transmitted using OTT connection 550.

Communication system 500 further includes base station 520 provided in atelecommunication system and comprising hardware 525 enabling it tocommunicate with host computer 510 and with UE 530. Hardware 525 mayinclude communication interface 526 for setting up and maintaining awired or wireless connection with an interface of a differentcommunication device of communication system 500, as well as radiointerface 527 for setting up and maintaining at least wirelessconnection 570 with UE 530 located in a coverage area (not shown in FIG.8) served by base station 520. Communication interface 526 may beconfigured to facilitate connection 560 to host computer 510. Connection560 may be direct, or it may pass through a core network (not shown inFIG. 8) of the telecommunication system and/or through one or moreintermediate networks outside the telecommunication system. In theembodiment shown, hardware 525 of base station 520 further includesprocessing circuitry 528, which may comprise one or more programmableprocessors, application-specific integrated circuits, field programmablegate arrays or combinations of these (not shown) adapted to executeinstructions. Base station 520 further has software 521 storedinternally or accessible via an external connection.

Communication system 500 further includes UE 530 already referred to.Its hardware 535 may include radio interface 537 configured to set upand maintain wireless connection 570 with a base station serving acoverage area in which UE 530 is currently located. Hardware 535 of UE530 further includes processing circuitry 538, which may comprise one ormore programmable processors, application-specific integrated circuits,field programmable gate arrays or combinations of these (not shown)adapted to execute instructions. UE 530 further comprises software 531,which is stored in or accessible by UE 530 and executable by processingcircuitry 538. Software 531 includes client application 532. Clientapplication 532 may be operable to provide a service to a human ornon-human user via UE 530, with the support of host computer 510. Inhost computer 510, an executing host application 512 may communicatewith the executing client application 532 via OTT connection 550terminating at UE 530 and host computer 510. In providing the service tothe user, client application 532 may receive request data from hostapplication 512 and provide user data in response to the request data.OTT connection 550 may transfer both the request data and the user data.Client application 532 may interact with the user to generate the userdata that it provides.

It is noted that host computer 510, base station 520 and UE 530illustrated in FIG. 8 may be similar or identical to host computer 430,one of base stations 412 a, 412 b, 412 c and one of UEs 491, 492 of FIG.7, respectively. This is to say, the inner workings of these entitiesmay be as shown in FIG. 5 and independently, the surrounding networktopology may be that of FIG. 7.

In FIG. 8, OTT connection 550 has been drawn abstractly to illustratethe communication between host computer 510 and UE 530 via base station520, without explicit reference to any intermediary devices and theprecise routing of messages via these devices. Network infrastructuremay determine the routing, which it may be configured to hide from UE530 or from the service provider operating host computer 510, or both.While OTT connection 550 is active, the network infrastructure mayfurther take decisions by which it dynamically changes the routing(e.g., based on load balancing consideration or reconfiguration of thenetwork).

Wireless connection 570 between UE 530 and base station 520 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to UE 530 using OTT connection 550,in which wireless connection 570 forms the last segment. More precisely,the teachings of these embodiments may improve the signaling overheadand reduce latency, which may provide faster internet access for users.

A measurement procedure may be provided for monitoring data rate,latency and other factors on which the one or more embodiments improve.There may further be an optional network functionality for reconfiguringOTT connection 550 between host computer 510 and UE 530, in response tovariations in the measurement results. The measurement procedure and/orthe network functionality for reconfiguring OTT connection 550 may beimplemented in software 511 and hardware 515 of host computer 510 or insoftware 531 and hardware 535 of UE 530, or both. In embodiments,sensors (not shown) may be deployed in or in association withcommunication devices through which OTT connection 550 passes; thesensors may participate in the measurement procedure by supplying valuesof the monitored quantities exemplified above, or supplying values ofother physical quantities from which software 511, 531 may compute orestimate the monitored quantities. The reconfiguring of OTT connection550 may include message format, retransmission settings, preferredrouting etc.; the reconfiguring need not affect base station 520, and itmay be unknown or imperceptible to base station 520. Such procedures andfunctionalities may be known and practiced in the art. In certainembodiments, measurements may involve proprietary UE signalingfacilitating host computer 510's measurements of throughput, propagationtimes, latency and the like. The measurements may be implemented in thatsoftware 511 and 531 causes messages to be transmitted, in particularempty or ‘dummy’ messages, using OTT connection 550 while it monitorspropagation times, errors etc.

FIG. 9 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 7 and 8. Forsimplicity of the present disclosure, only drawing references to FIG. 9will be included in this section.

In step 610, the host computer provides user data. In substep 611 (whichmay be optional) of step 610, the host computer provides the user databy executing a host application. In step 620, the host computerinitiates a transmission carrying the user data to the UE. In step 630(which may be optional), the base station transmits to the UE the userdata which was carried in the transmission that the host computerinitiated, in accordance with the teachings of the embodiments describedthroughout this disclosure. In step 640 (which may also be optional),the UE executes a client application associated with the hostapplication executed by the host computer.

FIG. 10 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 7 and 8. Forsimplicity of the present disclosure, only drawing references to FIG. 10will be included in this section.

In step 710 of the method, the host computer provides user data. In anoptional substep (not shown) the host computer provides the user data byexecuting a host application. In step 720, the host computer initiates atransmission carrying the user data to the UE. The transmission may passvia the base station, in accordance with the teachings of theembodiments described throughout this disclosure. In step 730 (which maybe optional), the UE receives the user data carried in the transmission.

FIG. 11 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 7 and 8. Forsimplicity of the present disclosure, only drawing references to FIG. 11will be included in this section.

In step 810 (which may be optional), the UE receives input data providedby the host computer. Additionally, or alternatively, in step 820, theUE provides user data. In substep 821 (which may be optional) of step820, the UE provides the user data by executing a client application. Insubstep 811 (which may be optional) of step 810, the UE executes aclient application which provides the user data in reaction to thereceived input data provided by the host computer. In providing the userdata, the executed client application may further consider user inputreceived from the user. Regardless of the specific manner in which theuser data was provided, the UE initiates, in substep 830 (which may beoptional), transmission of the user data to the host computer. In step840 of the method, the host computer receives the user data transmittedfrom the UE, in accordance with the teachings of the embodimentsdescribed throughout this disclosure.

FIG. 12 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 7 and 8. Forsimplicity of the present disclosure, only drawing references to FIG. 12will be included in this section.

In step 910 (which may be optional), in accordance with the teachings ofthe embodiments described throughout this disclosure, the base stationreceives user data from the UE. In step 920 (which may be optional), thebase station initiates transmission of the received user data to thehost computer. In step 930 (which may be optional), the host computerreceives the user data carried in the transmission initiated by the basestation.

The term unit may have conventional meaning in the field of electronics,electrical devices and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

Modifications, additions, or omissions may be made to the systems andapparatuses disclosed herein without departing from the scope of theinvention. The components of the systems and apparatuses may beintegrated or separated. Moreover, the operations of the systems andapparatuses may be performed by more, fewer, or other components.Additionally, operations of the systems and apparatuses may be performedusing any suitable logic comprising software, hardware, and/or otherlogic. As used in this document, “each” refers to each member of a setor each member of a subset of a set.

Modifications, additions, or omissions may be made to the methodsdisclosed herein without departing from the scope of the invention. Themethods may include more, fewer, or other steps. Additionally, steps maybe performed in any suitable order.

The foregoing description sets forth numerous specific details. It isunderstood, however, that embodiments may be practiced without thesespecific details. In other instances, well-known circuits, structuresand techniques have not been shown in detail in order not to obscure theunderstanding of this description. Those of ordinary skill in the art,with the included descriptions, will be able to implement appropriatefunctionality without undue experimentation.

References in the specification to “one embodiment,” “an embodiment,”“an example embodiment,” etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to implement such feature, structure, orcharacteristic in connection with other embodiments, whether or notexplicitly described.

Although this disclosure has been described in terms of certainembodiments, alterations and permutations of the embodiments will beapparent to those skilled in the art. Accordingly, the above descriptionof the embodiments does not constrain this disclosure. Other changes,substitutions, and alterations are possible without departing from thespirit and scope of this disclosure, as defined by the claims below.

At least some of the following abbreviations may be used in thisdisclosure. If there is an inconsistency between abbreviations,preference should be given to how it is used above. If listed multipletimes below, the first listing should be preferred over any subsequentlisting(s).

-   -   1×RTT CDMA2000 1× Radio Transmission Technology    -   3GPP 3rd Generation Partnership Project    -   5G 5th Generation    -   ABS Almost Blank Subframe    -   ARQ Automatic Repeat Request    -   AWGN Additive White Gaussian Noise    -   BCCH Broadcast Control Channel    -   BCH Broadcast Channel    -   CA Carrier Aggregation    -   CC Carrier Component    -   CCCH SDU Common Control Channel SDU    -   CDMA Code Division Multiplexing Access    -   CGI Cell Global Identifier    -   CIR Channel Impulse Response    -   CP Cyclic Prefix    -   CPICH Common Pilot Channel    -   CQI Channel Quality information    -   C-RNTI Cell RNTI    -   CSI Channel State Information    -   DCCH Dedicated Control Channel    -   DL Downlink    -   DM Demodulation    -   DMRS Demodulation Reference Signal    -   DRX Discontinuous Reception    -   DTX Discontinuous Transmission    -   DTCH Dedicated Traffic Channel    -   DUT Device Under Test    -   E-CID Enhanced Cell-ID (positioning method)    -   E-SMLC Evolved-Serving Mobile Location Centre    -   ECGI Evolved CGI    -   eNB E-UTRAN NodeB    -   ePDCCH enhanced Physical Downlink Control Channel    -   E-SMLC evolved Serving Mobile Location Center    -   E-UTRA Evolved UTRA    -   E-UTRAN Evolved UTRAN    -   FDD Frequency Division Duplex    -   GERAN GSM EDGE Radio Access Network    -   gNB Base station in NR    -   GNSS Global Navigation Satellite System    -   GSM Global System for Mobile communication    -   HARQ Hybrid Automatic Repeat Request    -   HO Handover    -   HSPA High Speed Packet Access    -   HRPD High Rate Packet Data    -   LOS Line of Sight    -   LPP LTE Positioning Protocol    -   LTE Long-Term Evolution    -   MAC Medium Access Control    -   MBMS Multimedia Broadcast Multicast Services    -   MBSFN Multimedia Broadcast multicast service Single Frequency        Network    -   MBSFN ABS MBSFN Almost Blank Subframe    -   MDT Minimization of Drive Tests    -   MIB Master Information Block    -   MME Mobility Management Entity    -   MSC Mobile Switching Center    -   NPDCCH Narrowband Physical Downlink Control Channel    -   NR New Radio    -   OCNG OFDMA Channel Noise Generator    -   OFDM Orthogonal Frequency Division Multiplexing    -   OFDMA Orthogonal Frequency Division Multiple Access    -   OSS Operations Support System    -   OTDOA Observed Time Difference of Arrival    -   O&M Operation and Maintenance    -   PBCH Physical Broadcast Channel    -   P-CCPCH Primary Common Control Physical Channel    -   PCell Primary Cell    -   PCFICH Physical Control Format Indicator Channel    -   PDCCH Physical Downlink Control Channel    -   PDP Profile Delay Profile    -   PDSCH Physical Downlink Shared Channel    -   PGW Packet Gateway    -   PHICH Physical Hybrid-ARQ Indicator Channel    -   PLMN Public Land Mobile Network    -   PMI Precoder Matrix Indicator    -   PRACH Physical Random Access Channel    -   PRS Positioning Reference Signal    -   PSS Primary Synchronization Signal    -   PUCCH Physical Uplink Control Channel    -   PUSCH Physical Uplink Shared Channel    -   RACH Random Access Channel    -   QAM Quadrature Amplitude Modulation    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RLM Radio Link Management    -   RNC Radio Network Controller    -   RNTI Radio Network Temporary Identifier    -   RRC Radio Resource Control    -   RRM Radio Resource Management    -   RS Reference Signal    -   RSCP Received Signal Code Power    -   RSRP Reference Symbol Received Power OR Reference Signal        Received Power    -   RSRQ Reference Signal Received Quality OR Reference Symbol        Received Quality    -   RSSI Received Signal Strength Indicator    -   RSTD Reference Signal Time Difference    -   SCH Synchronization Channel    -   SCell Secondary Cell    -   SDU Service Data Unit    -   SFN System Frame Number    -   SGW Serving Gateway    -   SI System Information    -   SIB System Information Block    -   SNR Signal to Noise Ratio    -   SON Self Optimized Network    -   SS Synchronization Signal    -   SSS Secondary Synchronization Signal    -   TDD Time Division Duplex    -   TDOA Time Difference of Arrival    -   TOA Time of Arrival    -   TSS Tertiary Synchronization Signal    -   TTI Transmission Time Interval    -   UE User Equipment    -   UL Uplink    -   UMTS Universal Mobile Telecommunication System    -   USIM Universal Subscriber Identity Module    -   UTDOA Uplink Time Difference of Arrival    -   UTRA Universal Terrestrial Radio Access    -   UTRAN Universal Terrestrial Radio Access Network    -   WCDMA Wide CDMA    -   WLAN Wide Local Area Network

1. A method performed by a wireless device for decoding public landmobile network (PLMN) information, the method comprising: receiving amessage comprising PLMN information, the PLMN information comprisingidentification information for a plurality of cells, the plurality ofcells are all associated with a first core network type; determiningfrom the PLMN information that at least one cell of the plurality ofcells is also associated with a second core network type; and accessinga first cell, the first cell associated with both the first core networktype and the second core network type.
 2. The method of claim 1, whereinthe PLMN information of the message comprises a first list of cellsassociated with the first core network type and a second list of cellsthat are associated with both the first core network type and the secondcore network type.
 3. The method of claim 1, wherein determining fromthe PLMN information that at least one cell of the plurality of cells isalso associated with a second core network type comprises, for each cellof the second group of cells that is also associated with the firstgroup of cells, following a reference to the PLMN information in thefirst group of cells.
 4. The method of claim 1, wherein the message is asystem information block message.
 5. The method of claim 1, wherein themessage is a radio resource control (RRC) message.
 6. The method ofclaim 1, wherein the first core network type is an enhanced packet core(EPC).
 7. The method of claim 1, wherein the second core network type isa 5G core (5GC).
 8. A wireless device operable to decode public landmobile network (PLMN) information, the wireless device comprisingprocessing circuitry operable to: receive a message comprising PLMNinformation, the PLMN information comprising identification informationfor a plurality of cells, the plurality of cells are all associated witha first core network type; determine from the PLMN information that atleast one cell of the plurality of cells is also associated with asecond core network type; and access a first cell, the first cellassociated with both the first core network type and the second corenetwork type.
 9. The wireless device of claim 8, wherein the PLMNinformation of the message comprises a first list of cells associatedwith the first core network type and a second list of cells that areassociated with both the first core network type and the second corenetwork type.
 10. The wireless device of claim 8, wherein the processingcircuitry configured to determine that at least one cell of theplurality of cells is also associated with the second core networkcomprises processing circuitry configured to, for each cell of thesecond group of cells that is also associated with the first group ofcells, follow a reference to the PLMN information in the first group ofcells.
 11. The wireless device of claim 8, wherein the message is asystem information block message.
 12. The wireless device of claim 8,wherein the message is a radio resource control (RRC) message.
 13. Thewireless device of claim 8, wherein the first core network type is anenhanced packet core (EPC).
 14. The wireless device of claim 8, whereinthe second core network type is a 5G core (5GC).